Add a trust-level parameter to configure the special remote #258
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thx for this. I am wondering now, whether this is equivalent in terms of outcome to running |
|
I decided to leave this here, and not put it into the 1.0 release. For reasons of timing and uncertainty re side-effect alone. Thx for implementing it, and sorry for not merging it now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This add a new parameter
--trust-leveltoadd-sibling-dataverse. Setting this parameter allows setting the trust level of the special remote (otherwise, git-annex's default is used when setting it up).It might be a fix for #179; it mimics how
create-sibling-riadoes it (though performs the trust setting via config variable instead of using e.g.,git annex trust, as I found its easier to streamline this way and doesn't require--force)